Categorizing digital content providers

ABSTRACT

The examples provide a content item distributor computing system that is configured to determine characteristics of content providers and providing content items to certain categories of content providers. In one embodiment, the content item distributor receives a request from a content provider to receive content items and determines if a provided set of video content has a minimum number of viewers and meets a standard for upload content. In response to the determination, the content item distributor communicates a content item to the video content provider to present in conjunction with video content.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 14/322,493, filed Jul. 2, 2014, and entitled“Monetization of Digital Content Contributions,” which is a continuationof U.S. patent application Ser. No. 12/115,512, filed on May 5, 2008,and entitled “Monetization of Digital Content Contributions,” now U.S.Pat. No. 8,924,270 issued on Dec. 30, 2014, which claims the benefit ofU.S. Provisional Application 60/927,940, filed May 3, 2007. The completedisclosure of the above-identified priority applications is hereby fullyincorporated herein by reference.

TECHNICAL FIELD

The examples described herein provide a content item distributorconfigured to categorize video content providers. In particular, theexamples are directed towards determining characteristics of contentproviders and providing content items to certain categories of contentproviders.

BACKGROUND

Content item distributors provide content items to video contentproviders to be presented to users with electronic documents or videos.The content item distributors determine which video content providersshould receive content items. The content items may be presented before,after, or in conjunction with the electronic documents or videos.

SUMMARY

The present examples of the technology provide methods and systems thatenable content item distributors to categorize video content providers.Content item distributors receive a request from a provider of videocontent to receive content items to present in conjunction with videocontent presented by the video content provider and analyzes a set ofvideo content presented by the video content provider. The content itemdistributor determines if the set of video content has a minimum numberof viewers and meets a standard for upload content. In response todetermining that the set of video content has the minimum number ofviewers and meets the standard for upload content and originality, thecontent item distributor communicates a content item to the videocontent provider to present in conjunction with video content.

In order for a video digital content provider to participate inreceiving content items to be presented with the digital content, thecontent provider submits an application to become a revenue sharingpartner. The application is analyzed by an application analysis moduleto determine whether the video content provider is eligible to receivecontent items based at least in part on the number of violations thatthe video content provider has received in addition to an applicationscore. Alternatively, the content item distributor invites contentproviders to receive content items based at least in part on anapplicant's pre-score.

Once a video content provider has been approved, the video contentprovider can determine which of their already-uploaded digital contentitems will be submitted for receiving content items. Alternatively, thevideo content provider can specify that digital video content will besubmitted during the initial upload of the digital content item to thecontent item distributor.

In one embodiment, the analysis module receives the request formonetization associated with the video content provider's digital videocontent and determines whether the digital video content is eligible.The determination whether digital video content is eligible is based atleast in part on various criteria including whether the digital videocontent includes only original content. Once digital video content hasbeen approved, content items stored in a content item database aredisplayed in conjunction with the digital video content.

The features and advantages described in this summary and the followingdetailed description are not all inclusive. Many additional features andadvantages will be apparent to one of ordinary skill in the art in viewof the drawings, specification and claims hereof.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of the system architecture of one embodimentof the present invention.

FIG. 2 illustrates a method for promoting a content provider to arevenue sharing partner in accordance with one embodiment of the presentinvention.

FIG. 3 illustrates a method for determining whether a content provideris eligible to become a revenue sharing partner in accordance with oneembodiment of the present invention.

FIG. 4 illustrates a method for enabling monetization of a video inaccordance with one embodiment of the present invention.

FIG. 5 illustrates a method for analyzing a video to determine whetherthe video should be enabled for monetization in accordance with oneembodiment of the present invention.

FIGS. 6-8 illustrate examples of user interfaces that are used bycontent providers during the application process to become a revenuesharing partner in accordance with one embodiment of the presentinvention.

FIG. 9 illustrates an example user interface that is used by a systemadministrator to assist in reviewing information regarding contentproviders who have requested to become a revenue sharing partner inaccordance with one embodiment of the present invention.

FIG. 10 illustrates an example of a user interface that informs contentsharing partners of important information of the revenue sharing partnerprogram in accordance with one embodiment of the present invention.

FIGS. 11-14 illustrate examples of user interfaces that are used bycontent sharing partners to review and upload videos for monetization inaccordance with one embodiment of the present invention.

FIG. 15 illustrates an example of a user interface illustrating amonetized video and an associated web advertisement that generatesrevenue in accordance with one embodiment of the present invention.

The figures depict a preferred embodiment of the present invention forpurposes of illustration only. One skilled in the art will readilyrecognize from the following discussion that alternative embodiments ofthe structures and methods illustrated herein may be employed withoutdeparting from the principles of the invention described herein.

DETAILED DESCRIPTION

System Overview

Referring now to FIG. 1, there is shown a system architecture of anembodiment of a video hosting website 100 in accordance with oneembodiment of the present invention. In certain examples, the videohosting website may be the content item distributor. As shown in FIG. 1,the video hosting website 100 comprises a video serving module 110, aningest module 115, an application analysis module 120, a video analysismodule 130, a revenue generation module 135, a front end server 140, auser database 150, a video database 155 and an advertisement database190. Many conventional features, such as firewalls, load balancers,application servers, failover servers, site management tools and soforth are not shown so as not to obscure the features of the system. Asuitable website for implementation of the system is the YOUTUBE™website, found at www.youtube.com; other video hosting sites are knownas well, and can be adapted to operate according to the teachingdisclosed herein. It will be understood that the term “website”represents any computer system adapted to serve content using anyinternetworking protocols, and is not intended to be limited to contentuploaded or downloaded via the Internet or the HTTP protocol. Ingeneral, functions described in one embodiment as being performed on theserver side can also be performed on the client side in otherembodiments if appropriate. In addition, the functionality attributed toa particular component can be performed by different or multiplecomponents operating together.

The server is implemented as server program executing on server-classcomputer comprising a CPU, memory, network interface, peripheralinterfaces, and other well known components. The computers themselvespreferably run an open-source operating system such as LINUX, havegenerally high performance CPUs, 1 G or more of memory, and 100 G ormore of disk storage. Of course, other types of computers can be used,and it is expected that as more powerful computers are developed in thefuture, they can be configured in accordance with the teachings here.The functionality implemented by any of the elements can be providedfrom computer program products that are stored in tangible computerreadable storage mediums (e.g., RAM, hard disk, or optical/magneticmedia).

A client 170 executes a browser 171 to view digital content items andcan connect to the front end server 140 via a network 180, which istypically the internet, but can also be any network, including but notlimited to any combination of a LAN, a MAN, a WAN, a mobile, wired orwireless network, a private network, or a virtual private network. Whileonly a single client 170 and browser 171 are shown, it is understoodthat very large numbers (e.g., millions) of clients are supported andcan be in communication with the video hosting website 100 at any time.The client 170 may include a variety of different computing devices.Examples of client devices 170 are personal computers, digitalassistants, personal digital assistants, cellular phones, mobile phones,smart phones or laptop computers. As will be obvious to one of ordinaryskill in the art, the present invention is not limited to the deviceslisted above.

The browser 171 can include any application that allows users of client170 to access web pages on the World Wide Web. Suitable applications areMicrosoft Internet Explorer, Netscape Navigator, Mozilla Firefox, AppleSafari or any application adapted to allow access to web pages on theWorld Wide Web. The browser 171 can also include a video player (e.g.,Flash™ from Adobe Systems, Inc.), or any other player adapted for thevideo file formats used in the video hosting website 100. Alternatively,videos can be accessed by a standalone program separate from the browser171. A user can access a video from the video hosting website 100 bybrowsing a catalog of videos, conducting searches on keywords, reviewingplay lists from other users or the system administrator (e.g.,collections of videos forming channels), or viewing videos associatedwith particular user groups (e.g., communities).

A content provider 185 is an entity that owns or controls at least someof the rights to a particular work, such as a video content provider.The content provider 185 may be an individual, a group of individuals,or an entity such as a music or video production company or studio orartists' group. The content provider 185 is responsible for providingdigital content items to the video hosting website 100 via the network180. The content provider 185 determines digital content items thatshould be uploaded to the video hosting website 100 and that may beeligible to generate revenue on the video hosting website 100.Additionally, the content provider 185 may also upload digital contentitems to the video hosting website 100 regardless of whether the digitalcontent items are eligible to generate revenue. While only one contentprovider 185 is shown, it is understood that any number of contentproviders are supported and can be in communication with the videohosting website 100 at any time. Additionally, content provider 185 maybe referred to below as a “revenue sharing partner.”

The uploaded digital content items can include, for example, video,audio or a combination of video and audio. Alternatively, a digitalcontent item may be a still image, such as a JPEG or GIF file or a textfile. For purposes of convenience and the description of one embodiment,the uploaded digital content items will be referred to as a “video,”“video files,” or “video items,” but no limitation on the type ofdigital content items that can be uploaded are indented by thisterminology. Thus, the operations described herein for enablingmonetization of a digital content item can be applied to any type ofdigital content, non only videos; other suitable types of digitalcontent items include audio files (e.g. music, podcasts, audio books,and the like), documents, websites, images, multimedia presentations,and so forth.

As previously mentioned, users of clients 170 execute a browser 171 andconnect to the front end server 140 to view the videos that have beenuploaded from the content providers 185. Users of client 170 can searchfor videos based on keywords, tags or other metadata. These requests arereceived as queries by the front end server 140 and provided to thevideo serving module 110, which is responsible for searching the videodatabase 155 for videos that satisfy the user queries and providing thevideos to the users. The video serving module 110 supports searching onany fielded data for a video, including its title, description, tags,author, category and so forth. Alternatively, users can browse a list ofvideos based on categories such as most viewed videos, sports, animals,or automobiles. For example, the user may browse a list of videosrelated to cars and select which videos from the list to view.

While viewing a video on the video hosting website 100, a user may alsobe shown a web advertisement in conjunction with the video if the videohas been enabled for monetization. The advertisement database 190 isresponsible for storing web advertisements that are associated withvideos that have been enabled for monetization. Through viewerinteraction with the web advertisement, the content provider 185associated with the video receives a share of the revenue generated bythe advertisement. The revenue generation module 135 is responsible fortracking revenue that content providers 185 generate from webadvertisements placed in conjunction with their monetized videos. Videosthat have been enabled for monetization may also be shown as embeddedvideos 177 on websites 175 other than the video hosting website 100.

In an alternative embodiment, users of client 170 can also uploaddigital content items to the video hosting website 100 which may beeligible to generate revenue on the video hosting website 100. For easeof discussion, only content providers 185 are responsible for uploadingdigital content items though users of client 170 can also upload digitalcontent items to the video hosting website 100.

To upload videos to the video hosting website 100, a content provider185 connects to the front end server 140 via the network 180. Theuploaded videos are processed by an ingest module 115, which processesthe videos for storage in the video database 155. This processing caninclude format conversion (transcoding), compression, metadata tagging,and other data processing. The ingest module 115 processes the videos inorder to standardize content for playback to users of client 170. Thisenables the video hosting website 100 to receive uploaded videos ofvarious formats, while still being able to provide a standardized outputto users. An uploaded video file is associated with the content provider185 and the content provider's account record is updated in the userdatabase 150 as needed.

The video database 155 is used to store the ingested videos. The videodatabase 155 stores video content and associated metadata provided bytheir respective content owners. Each uploaded video is assigned a videoidentifier (id) when it is processed by the ingest module 115. The videofiles have metadata associated with each file such as a video ID,artist, video title, label, genre, time length, and optionallygeo-restrictions that can be used for data collection or contentblocking on a geographic basis.

The user database 150 is responsible for maintaining a record of allregistered users of the video hosting website 100. Registered usersinclude content providers 185 and/or users who simply view videos on thevideo hosting website 100. Each content provider 185 and/or individualuser registers account information including login name, electronic mail(e-mail) address and password with the video hosting website 100. Thisaccount information is stored in the user database 150. Additionally,the user database 150 stores each user's infraction informationindicating the number of received violations, type of violations anddate of the violation. Infractions are violations of the rules ofconduct of the video hosting website 100 as further discussed below. Theuser database 150 also stores a record of every video that each contentprovider 185 has uploaded to the video hosting website 100.

The application analysis module 120 is responsible for analyzingrequests from content providers 185 to become revenue sharing partners.Revenue sharing partners receive shared revenue from their uploadedvideos and are considered independent video creators who are seekingonline distribution of their videos. Generally, revenue sharing partnerscreate original videos which generate a large amount of traffic (i.e.,users viewing videos) on the video hosting website 100. Original videosare videos that are entirely of content that the content provider 185associated with the video have created. Examples of original videos thatwould be eligible for monetization are further described below in regardto the video monetization process.

Revenue sharing partners receive a share of the revenue generated fromad impressions occurring when videos that have been enabled formonetization are viewed by users of the video hosting web site 100. Inone embodiment, a content provider 185 submits an application to thevideo hosting website 100 to become a revenue sharing partner. The frontend server 140 forwards the application to the application analysismodule 120 which analyzes the application to determine whether thecontent provider 185 is eligible to become a revenue sharing partner.

Once the content provider's request to become a revenue sharing partnerhas been granted, the user's account information is updated in the userdatabase 150 to indicate that the content provider 185 is now a revenuesharing partner. For ease of discussion, content providers 185 that havebecome eligible to receive shared revenue associated with their videoswill be called a “revenue sharing partner” or “revenue sharingpartners.”

Revenue sharing partners may elect to monetize videos during an initialupload to the video hosting website 100 or may monetize videos that havebeen previously uploaded. The video analysis module 130 is responsiblefor analyzing the videos that have been submitted for monetization. Inone embodiment, the video analysis module 130 checks the video acrossreference sources to assist in the determination that the contentincluded in the video is original material. Systems and methods formatching uploaded digital content items against reference content areknown, and some are described for example in U.S. patent applicationSer. Nos. 11/765,292 and 11/746,339, each of which is incorporated byreference herein in its entirety. In one embodiment, once a video hasbeen determined to be original, the video is further analyzed based oncriteria such as popularity to determine whether the video should bemonetized, as further described below in the video monetization process.

Revenue Sharing Partner Application Process

The revenue sharing partner application process is performed by theapplication analysis module 120 to determine whether a content provider185 is eligible to become a revenue sharing partner. As previouslydiscussed, a revenue sharing partner receives a share of the revenuegenerated from ad impressions occurring when monetized videos associatedwith the revenue sharing partner are viewed by users of the videohosting website 100.

Referring now to FIG. 2, the revenue sharing partner application processaccording to one embodiment has the following functional stages:

201: Receiving a revenue sharing partner request;

203: Determining whether to allow the content provider to participate inrevenue sharing; and

205: Notifying content provider of decision.

The first stage 201 is a process repeated for every content provider 185who decides to participate in revenue sharing of their videos.Generally, in the first stage 201 the application analysis module 120receives a revenue sharing partner request from a content provider 185.Referring to FIG. 6, there is shown one embodiment of a user interfacethat provides information about the revenue sharing partner program to acontent provider interested in receiving shared revenue for his or heruploaded videos. The content provider 185 views an information web page601 of the revenue sharing partner program that informs the contentprovider 185 of the benefits of becoming a revenue sharing partner andthe qualifications needed to become a revenue sharing partner. Thecontent provider reviews the information web page 601 and if the contentprovider 185 is interested in becoming a revenue sharing partner, thecontent provider clicks on the apply now button 603 which directs thecontent provider to a web page containing a revenue sharing application.

Referring to FIG. 7, there is shown a web page containing the revenuesharing partner application 701. The content provider 185 entersinformation into data entry fields of the revenue sharing partnerapplication 701 which will be analyzed to determine whether to allow thecontent provider 185 to become a revenue sharing partner. The contentprovider 185 provides personal information 703 such as their first andlast name and their date of birth along with business information 705such as their company name and/or website. The content provider 185 mustalso provide information regarding other accounts on the video hostingwebsite 100 that should be included in the revenue sharing partnerapplication 701. Generally, the content provider 185 is not required toprovide information for every category. The required data entry fieldsare donated by an asterisk 713 or any other graphical symbol to indicatethat the video hosting website 100 requires content providers 185 toprovide information pertaining to the particular data entry field inorder to complete the revenue sharing partner application 701.

Required fields include the content providers 185 first and last namealong with their date of birth, for example. In one embodiment, contentproviders 185 must be 18 years of age or older to become a revenuesharing partner. Additionally, the content providers 185 must providetheir country of residence as in one embodiment, only revenue sharingapplications from defined geographic areas are acceptable.

One of the most important required fields pertains to the videoinformation 707 section. Content providers 185 are required to expressthe amount of videos that they have created or produced. In oneembodiment, content providers 185 specify a range of videos that theyhave created/produced from a pull down menu such as 11 to 30 videos, forexample. Alternatively, content providers 185 can manually provide anexact number or estimate of created/produced videos.

A content provider is also required to indicate how often he/she createsand uploads new videos. The number of videos created/produced andfrequency of uploads associated with the content provider 185 isimportant as this is a strong indication of the amount of viewingtraffic (i.e., from users of the video hosting website 100) that thecontent provider 185 may generate. Additionally, the miscellaneousinformation pertaining to the content provider's videos is also requiredsuch as the average length of the content providers' 185 videos and thecategory that best describes the videos such as comedy, automobiles,nature, or instructional videos. Through statistical analysis of theamount of revenue generated in the past regarding videos of a particularcategory, the category information is important as a precedent may beset that videos in a particular category typically provide the mostrevenue. For example, a pattern may have developed that contentproviders 185 who upload videos categorized as comedy generally generatethe most revenue in the video hosting website 100. Thus, the categoryinformation is important as it indicates the amount of revenue thatcontent providers 185 may potentially generate.

Additionally, though not required, content providers 185 are allowed togive a written explanation of why they want to join the revenue sharingpartner program. Content providers leave their explanation in anexplanation box 711 giving their reasoning. For example, a contentprovider 185 may leave the explanation stating “I have been a member ofthe YouTube community since 2006. I have uploaded more than 200 originalvideos and my channel has over 2000 subscribers. I would like to jointhe Partner Program so I can earn revenue for my work.” In oneembodiment, the written explanation is manually reviewed by a systemadministrator or person associated with the video hosting website 100 toassist in determining whether the content provide 185 should be allowedto become a revenue sharing partner. Alternatively, the applicationanalysis module 120 may parse the explanation for meaningful keywords orphrases in the text such as “uploaded more than 200 original videos” or“member since 2006.” These keywords or phrases can later be analyzed toassist in the revenue sharing partner application process.

Once the content provider 185 has answered all the required data entryfields in the revenue sharing partner application 701, the contentprovider 185 clicks on the review application button 715. Referring toFIG. 8, there is shown one embodiment of a user confirmation interface.Once the review application button 715 is clicked, the content provider185 is directed to a confirmation page 801 where the content provider185 reviews the accuracy of the provided information prior to submittingthe application via the submit application button 803.

Referring back to FIG. 2, the second stage 203 is a process where theapplication analysis module 120 determines whether to allow the contentprovider 185 associated with the received revenue sharing partnerapplication to participate in revenue sharing. FIG. 3 is representativeof the steps performed by the application analysis module 120 in thesecond stage 203. The second stage 203 comprises the followingfunctional steps to determine whether to admit the content provider 185into the revenue sharing partner program:

301: Analyzing infractions against content provider;

303: Determining content provider's application score; and

305: Analyzing videos based on video originality.

Referring now to FIG. 9, there is shown a partner signup list userinterface 901 that allows a system administrator of the video hostingwebsite 100 to view information regarding various content providers 185indicated in the Username column 903. Note that the partner signup listuser interface 901 is merely illustrative of one embodiment and otherarrangements of data collection and presentation may be used instead.The content providers 185 in the Username column 903 represent contentproviders 185 who have applied to the revenue sharing partner program.In step 301 (FIG. 3), the application analysis module 120 analyzesinfractions accumulated by a content provider 185 applying to therevenue sharing partner program. Infractions are violations of the rulesof conduct specified by the system administrator of the video hostingwebsite 100. Infractions can lead to takedown requests being issued by asystem administrator of the video hosting website 100 because a user ofthe video hosting website 100 flagged a video as inappropriate. Forexample, videos having inappropriate content can be classified as beingsexually explicit, drug promotion (i.e., through drug usage), acts ofanimal cruelty, graphic violence or spam. Videos of this nature can beflagged as inappropriate by users and a take down request may be issuedby the system administrator if the video is deemed inappropriate afterbeing reviewed. Alternatively, a system administrator may issue a takedown request without a video being flagged if a system administratordeems the video as inappropriate. The video is eventually removed fromthe video hosting website 100 if the take down request is validated.

Additionally, videos may be flagged as inappropriate because the contentprovider 185 is not authorized to use the content in the video. Forexample, television shows, music videos, music concerts or commercialsshould not be uploaded without permission from the owners of thecontent. Uploaded videos containing material not belonging to theuploading content provider may receive a takedown request because of acopyright violation.

When a takedown request is processed and a video is removed from thevideo hosting website 100, the content provider 185 associated with thevideo receives a strike against his or her account. Generally, a strikeis a violation of the rules of the content hosting website that led tothe removal of a video associated with a content provider 185 from thevideo hosting website 100. The strikes are accumulated in the contentprovider's account record stored in the user database 150. The strikesare generally classified under two categories: copyright strikes andmiscellaneous strikes. Copyright strikes are issued if a video wasremoved from the video hosting website 100 because the content provider185 did not own the material in the video. Thus, the content provider185 received a copyright strike due to an alleged copyright violation.

Miscellaneous strikes can be issued due to videos being removed from thevideo hosting website 100. Videos are removed from the video hostingwebsite 100 because a take down request may have been receivedindicating the video had inappropriate content. Additionally,miscellaneous strikes may be issued if other rules of conduct of thevideo hosting website 100 are violated. For example, if one contentprovider 185 is using an account of another content provider withoutproper consent, a miscellaneous strike may be issued. Additionally, ifthe content provider 185 is caught modifying part of the video hostingweb site 100 without proper consent from a system administrator amiscellaneous strike may be issued.

The application analysis module 120 analyzes the strikes against acontent provider 185 who has applied to become a revenue sharing partnerby reviewing the content provider's account information in the userdatabase 150 and extracting the number of copyright strikes andmiscellaneous strikes against the content provider 185. In oneembodiment, a summary of the strikes is included in a user interface 901under the Strikes Ok column 905 so that a system administrator canreview the information. The Strikes Ok column 905 comprises strikeinformation such as the number of miscellaneous strikes 913 and thenumber of copyright strikes 911 against the content provider 185.

The Strikes Ok column also includes a textual symbol indicating a strikestatus 909 of the content provider 185. The strike status 909 indicateswhether the content provider 185 has an amount of strikes againsthis/her account that is either tolerable or intolerable. A tolerablenumber of strikes indicate that the amount of strikes against a contentprovider 185 is not enough to justify the content provider 185 frombeing denied entry into the revenue sharing partner program. Anintolerable number of strikes indicate that the amount of strikesagainst a content provider 185 is an indication that the contentprovider 185 may not be eligible for the revenue sharing partnerprogram.

The textual symbol that indicates the strike status 909 will either beshown as a “Y” implying that the number of strikes against the contentprovider 185 is tolerable or a “N” implying that the number of strikesagainst the content provider 185 is not tolerable, for example. Anysymbol can be used to represent the strike status 909.

In one embodiment, the tolerability of the number of strikes isdependent on the type of strike against the content provider 185. If thenumber of copyright strikes 913 that a content provider 185 received isgreater than an intolerable threshold, such as one or more strikes (ortwo or more in some embodiments), the strike status would be “N”indicating that the number of copyright strikes 911 against the contentprovider 185 is intolerable. The number of strikes that would facilitatea strike status of “N” is reconfigurable and is determined by the systemadministrator of the video hosting website 100. In one embodiment, thecontent provider 185 is automatically denied from the revenue sharingpartner program if the strike status was intolerable because the highnumber of copyright strikes indicates that the content provider 185 hasa history of uploading copyrighted content. Alternatively, a systemadministrator may review the number of copyright strikes to determinewhether the content provider 185 is still eligible to join the revenuesharing partner program.

If the number of copyright strikes 913 is equal to a tolerablethreshold, such as one strike, then the application analysis module 120reviews the information associated with the copyright strike that isstored in the user database 150 to determine the amount of time that haspassed since the copyright strike was issued against the contentprovider 185. In one embodiment, if the copyright strike occurred morethan a predefined number of years from the present date, than the strikestatus would indicate “Y” that the strike status is tolerable. Forexample, if the copyright strike occurred more than 2 years from thepresent date, the strike status would indicate “Y.” In one embodiment,if the copyright strike occurred within a predefined number of years,the strike status would indicate “N” and the content provider 185 isautomatically denied from the revenue sharing partner program.

The miscellaneous strikes 911 information is configured in a similarmanner as the description relating to the copyright strikes 913. In oneembodiment, the application analysis module 120 analyzes the number ofcopyright strikes 913 and miscellaneous strikes 911 to determine thestrike status 909 against the content provider. Alternatively, thesystem administrator may analyze the copyright strikes 913 andmiscellaneous strikes 911 and determine the strike status 909.

In step 303, receiving a revenue sharing partner application prompts theapplication analysis module 120 to determine the content provider'sapplication score once the infractions against a content provider areanalyzed. The partner signup list user interface 901 also includes aFinal Score column 907. The Final Score column 907 indicates howvaluable the content provider 185 is to the video hosting website 100.In one embodiment, the value of the content provider 185 is measured ona scale from 0.0 to 10.0 according to various criteria where a score of10.0 indicates that the content provider 185 is a perfect candidate forthe revenue sharing partner program and a score of 0.0 indicates thatthe content provider 185 is not eligible for the revenue sharing partnerprogram.

The application analysis module 120 determines a final score, in oneembodiment, for every content provider 185 who submits a revenue sharingpartner application. The final score is determined using a final scorealgorithm comprised of the sum of weighted sub-scores, where each of thesub-scores is based on various criteria. The weighted sub-scores thatare used to determine the final score, in on embodiment includesubscribers sub-score, total views sub-score, views above 100 sub-score,views above 1000 sub-score, amount of videos sub-score, channel viewssub-score, and user feedback sub-score.

The relationships of these sub-scores to each other in an exemplaryembodiment is represented by the equation as follows:finScore=0.3·subscribe+0.05·totViews+0.1·view100+0.25·view1000+0.05·amtVid+0.15·chaView+0.1·feedbackwhere:

-   -   finScore=final score    -   subscribe=subscribers sub-score    -   totViews=total views sub-score    -   view100=views above 100 sub-score    -   view1000=views above 1000 sub-score    -   amtVid=amount of videos sub-score    -   chanView=channel views sub-score    -   feedback=user feedback sub-score        In the above equation, the various weighting parameters        preceding each sub-score are used for example purposes only and        any weighting value for each of the sub-scores can be used as        determined by the system administrator of the video hosting        website 100.

In one embodiment, the subscribers sub-score is a measure of long terminterest of the content provider's uploaded videos. A content provider185 is capable of setting up a channel associated with his or heraccount where the channel is a web page illustrating only videos relatedto the content provider 185. Users of the video hosting website 100 canjoin the content provider's channel in order to view videos that thecontent provider 185 has uploaded. In one embodiment, users join thecontent provider's channel by providing contact information including ane-mail address to the content provider 185, so that users can benotified when new videos are uploaded to the channel by the contentprovider 185.

Once a user has joined a content provider's channel web page, the useris said to be subscribed to the channel. Being subscribed to a channelallows the user to view videos in the channel and to receive updateswhen new videos are posted. In one embodiment, users of the videohosting website 100 that are not subscribed are still able to view thecontent provider's channel, but are not allowed to view (i.e., load orwatch) any of the videos in the channel. Alternatively, users of thevideo hosting website 100 that are not subscribed are able to watch thevideos in the channel, but do not receive updates when new videos areuploaded to the channel.

The subscribers sub-score is calculated based at least in part on thenumber of subscribers (i.e., users who have joined the content providerschannel). In one embodiment, the following variables are used in theequation representative of the calculation used to determine a rawsubscriber sub-score found below:

-   -   rawSub=raw subscriber sub-score    -   numSub=number of subscribers

The relationships of these variables to each other in an exemplaryembodiment is represented by the equation as follows:

${rawSub} = \frac{\log\left( \frac{numSub}{20} \right)}{\log(10)}$

For each of the sub-scores mentioned above, a raw sub-score iscalculated that will be used in a sub-score algorithm to determine thesub-scores value. For exemplary purposes, a raw sub-score for each ofthe sub-scores mentioned above will be calculated and used in thecalculation of an example final score for a content provider 185 whoapplied to become a revenue sharing partner. For example, assume thatthe number of subscribers to a content provider's channel is equal to600. Using this value, the calculation of the raw subscriber sub-scoreusing the above equation would result in a raw subscriber sub-score of1.48. The raw subscriber sub-score will be later used in the calculationof the subscriber sub-score.

In one embodiment, the total views sub-score is the total number ofviews that the content provider 185 has received for his or her uploadedvideos. The total number of views that the content provider 185 hasreceived indicates the total interest that users of the video hostingwebsite 100 have for the content provider's uploaded videos. In oneembodiment, the following variables are used in the equationrepresentative of the calculation used to determine a raw total viewssub-score found below:

-   -   rawTotViews=raw total views sub-score    -   numViews=total number of views the content provider has received        for his or her uploaded videos

The relationships of these variables to each other in an exemplaryembodiment is represented by the equation to determine the raw totalviews sub-score is as follows:

${rawTotViews} = \frac{\log\left( \frac{numViews}{10000} \right)}{\log(10)}$

For exemplary purposes of a calculation of a final score, assume thatthe total number of views the content provider 185 has received for hisor her uploaded videos is equal to 12,000 views. Using the aboveequation, the calculated raw total views sub-score is equal to 0.08. Theraw total views sub-score will be later used in the calculation of thetotal views sub-score.

In one embodiment, the views above 100 sub-score measures the totalinterest in the content provider's uploaded videos with a slightemphasis on popularity. The following variables are used in the equationrepresentative of the calculation used to determine a raw views above100 sub-score:

-   -   rawViews100=raw views above 100 sub-score    -   numViews=total number of views the content provider 185 received        for his or her uploaded videos    -   adjNumViews=numViews−100

In one embodiment, to determine the raw views above 100 sub-score, anadjusted value of the total number of views the content provider 185 hasreceived for his or her uploaded videos is calculated as represented bythe variable adjNumViews. Generally, to determine the adjusted value ofthe total number of views, in one embodiment a value of 100 issubtracted from the total number of views the content provider 185 hasreceived for his or her uploaded videos. The value of 100 is used todetermine a slight emphasis in popularity when determining the raw viewsabove 100 sub-score. If the value of adjNumViews is still greater than avalue of 0, the variable the adjNumViews will be set to the value. Sincethe adjusted number of total views is still a positive number, it isassumed that the content provider's video received enough views toindicate that his or her videos are slightly popular. Otherwise, theadjNumViews is equal to 0. The value of 100 is adjustable based on howmuch emphasis will be given on popularity and can be set to any value bythe system administrator of the video hosting website 100. For examplepurposes to calculate a raw total views above 100 sub-score, using thetotal number of views the content provider 185 received for his or heruploaded videos of 12,000 views from the calculation of the raw totalviews sub-score, the adjusted number of views is 11,900 views. Theadjusted number of views is used in the calculation of raw views above100 as shown below.

The relationships of the above variables to each other in an exemplaryembodiment is represented by the equation to determine the raw viewsabove 100 sub-score is as follows:

${{rawViews}\; 100} = \frac{\log\left( \frac{adjNumViews}{10000} \right)}{\log(10)}$

Using the above equation and the previously calculated adjusted numberof views, the raw views above 100 sub-score is equal to 0.075. The rawviews above 100 sub-score will be later used in the calculation of theviews above 100 sub-score.

In one embodiment, the views above 1000 sub-score measures the totalinterest in the content provider's uploaded videos with a strongemphasis on popularity. The following variables are used in the equationrepresentative of the calculation used to determine a raw views above1000 sub-score:

rawViews1000=raw views above 1000 sub-score

numViews=total number of views the content provider 185 received for hisor her uploaded videos

adjNumViews=numViews−1000

As previously discussed in regards to the calculation of the adjustedtotal number of views the content provider 185 has received for his orher uploaded videos in the calculation of the views above 100 sub-score,an adjusted total number of views must be calculated. The samecalculation is performed in the determination of the adjusted totalnumber of views except that a larger value is subtracted from the totalnumber of views rather than a value of 100. For example, to adjust thevalue of the total number of views, a value of 1,000 is subtracted todetermine the adjusted value of the total number of views that thecontent provider's videos have received. The value of 1000 isreconfigurable based on the amount of emphasis that will be given onpopularity and can be set to any value by the system administrator ofthe video hosting website. Generally, after adjusting the total numberof views that the content provider's videos have received, if the valueis still a positive value than the content provider's videos are said tobe popular and the adjNumViews is set to the positive value. Otherwise,the adjNumViews is set to zero. For example purposes to calculate a rawviews above 1000 sub-score, using the total number of views the contentprovider 185 received for his or her uploaded videos of 12,000 views,the adjusted number of views is 11,000 views.

The relationships of the variables described above to each other in anexemplary embodiment is represented by the equation to determine the rawviews above 1000 sub-score is as follows:

${{rawViews}\; 1000} = \frac{\log\left( \frac{adjNumViews}{10000} \right)}{\log(10)}$

Using the above equation and the previously calculated adjusted numberof views, the raw views above 1000 sub-score is equal to 0.04. The rawviews above 1000 sub-score will later be used in the calculation of theviews above 1000 sub-score.

In one embodiment, the amount of videos sub-score is factored into thefinal score as content providers 185 that have a large number ofuploaded videos associated with their account are preferred. The amountof videos that the content provider 185 has uploaded can be extractedfrom the revenue sharing partner application that was previouslydescribed above. Alternatively, the application analysis module 120 candetermine this amount from the content provider's account record in theuser database 150. Generally, content providers 185 with a large numberof uploaded videos have a potentially high revenue generating ability asthey have a large number of videos which web advertisements canpotentially be placed. Thus, content providers 185 with a large numberof uploaded videos are preferred. For example, a content provider 185with 30 uploaded videos would receive a higher amount of videossub-score compared to a content provider 185 with only 5 uploadedvideos. For example purposes to calculate a raw amount of videossub-score, a content provider 185 with 30 uploaded videos will be usedin the determination of the raw amount of videos sub-score.

The following variables are used in the equation representative of thecalculation used to determine a raw amount of videos sub-score:

numVid=number of uploaded videos associated with the content provider

rawAmtVid=raw amount of videos sub-score

The relationships of the above variables to each other in an exemplaryembodiment is represented by the equation to determine the raw number ofvideos sub-score is as follows:

${rawAmtVid} = \frac{\log({numVid})}{\log(4)}$

For the example of a content provider 185 with 30 uploaded videos, theraw amount of videos sub-score is equal to a value of 2.45 using theequation shown above. The raw amount of videos sub-score will later beused in the calculation of amount of videos sub-score.

In one embodiment, the channel views sub-score is calculated. Aspreviously discussed, a content provider 185 is capable of setting up achannel associated with his or her account where the channel is a webpage illustrating only videos related to the content provider 185. Thechannel views sub-score is calculated based at least in part on thenumber of views or hits a content provider 185 has received on his orher channel. The number of views (i.e., hits) represents the number ofusers of the video hosting website 100 who have viewed the contentprovider's channel. The number of views the channel has received isaccumulated from both subscribers of the channel and from users that arenot subscribed. Thus, when any user of the video hosting website 100views the content provider's channel, the user's act of viewing thechannel is considered a single view. The viewing information isaccumulated each time a user of the video hosting website 100 views thecontent provider's channel and is stored in the content provider'saccount record in the user database 150.

The following variables are used in the equation representative of thecalculation used to determine the channel views sub-score:

numChanViews=number of views (i.e., hits) a content provider hasreceived on his or her channel

rawChanViews=raw channel views sub-score

The relationships of the above variables to each other in an exemplaryembodiment is represented by the equation to determine the channel viewssub-score is as follows:

${rawChanViews} = \frac{\log\left( \frac{numChanViews}{1000} \right)}{\log(10)}$

For exemplary purposes, assume that a content provider 185 has received13,000 views on his or her channel. Accordingly, the raw channel viewssub-score calculated using the above equation is equal to a value of1.11. The raw channel views sub-score will later be used in thecalculation of the channel views sub-score.

In one embodiment, the feedback sub-score reflects the feedback that acontent provider's videos have received from users of the video hostingwebsite 100. Feedback can include a user providing a video rating suchas rating one of the content provider's videos with a star rating of 5out of 5 stars or users providing comments on a content provider'svideos indicating that the user enjoyed the video. Additionally,feedback can include the number of instances users of the video hostingwebsite 100 have bookmarked web pages containing the content provider'svideos to a favorites category. The act of a user bookmarking a videoindicates that the user may have enjoyed the video or found the videointeresting enough to keep a record of the web page containing the videofor future viewing. Videos that have been bookmarked in the user'sfavorites category are said to be favoritized. Each instance of a userbookmarking a video and the rating information provided by users isstored in the account record of the content provider 185 in the userdatabase 150 that is associated with the bookmarked video.

The following variables are used to determine feedback scores pertainingto the feedback that each of the content provider's video has received:

-   -   numRatingStars=total number of rating stars that the content        provider has received for his or her videos    -   numRatings=total number of users who provided a video rating        (i.e., rating stars)    -   numFav=sum of the total number of instances that each of the        content provider's video has been favoritized.

The variables shown above are used in the equations below to determinevarious feedback scores as follows:

     rawRatingSum = numRatingStars + (5 ⋅ numFav)     ratingWeight = numRatings + numFav${ratingSum} = {{rawRatingSum} - {e^{({- \frac{ratingWeight}{1000}})} \cdot \left( {{rawRatingSum} - \left( {2.5 \cdot {ratingWeight}} \right)} \right)}}$

In one embodiment, the rawRatingSum is a score that is based at least inpart on the amount of feedback received from users of the video hostingwebsite 100 with a weighting factor associated with the total number ofinstances that each of the content provider's video has beenfavoritized. The weighting factor can be adjusted by the systemadministrator of the video hosting website 100 in order to adjust theeffect of the videos which have been favoritized. Generally, therawRatingSum is the total amount of feedback received from users of thevideo hosting website. In one embodiment, the ratingWeight is a score isbased at least on the number of users of the video hosting website whohave left feedback.

For exemplary purposes, assume that a content provider 185 received atotal of 100 rating stars for his or her uploaded videos from 30 usersof the video hosting website 100. Additionally, assume that a totalnumber of 50 users of the video hosting website have favoritized a videoassociated with the content provider 185. Accordingly, the rawRating sumis equal to a value of 350 and the ratingWeight has a value of 80. Usingthese values, the calculated ratingSum is equal to a value of 211.5. Theabove feedback scores are then used as variables in the calculation ofthe raw feedback sub-score as follows:

${rawFeedback} = {{2 \cdot \left( \frac{ratingSum}{ratingWeight} \right)} - 6}$

For exemplary purposes, using the previously calculated feedback scores,the raw feedback sub-score is equal to a value of −0.7125. The rawfeedback sub-score will later be used in the calculation of the feedbacksub-score.

Each of the calculated raw sub-scores discussed above are now suitableto be used in the calculation of their respective sub-score. In oneembodiment, any raw sub-score that has a value of less than zero, thecorresponding sub-score is equal to zero. For example, in thecalculation of the raw feedback sub-score, the calculated raw sub-scoreis equal to a value of −0.7125. Thus, the feedback sub-score is equal tozero. Otherwise, in one embodiment the following equation isrepresentative of an equation used in the calculation of each sub-score:

${{sub}\text{-}{score}} = {20 \cdot \left( \frac{\alpha}{\alpha + 3} \right)}$

In the above equation, a is equal to any of the raw sub-scores that werepreviously described above. Each raw sub-score is used to calculate itsrespective sub-score, represented by the variable sub-score, using theequation above. For exemplary purposes, the previously calculated rawsub-scores are used to calculate example sub-scores for a contentprovider 185. Using the above equation and the previously calculated rawsub-scores, the calculated sub-scores are shown as follows:

Raw Sub-Score Value Sub-Score Value Subscribers sub-score 1.48 6.61Total views sub-score 0.08 0.52 Views above 100 sub-score 0.075 0.49Views above 1000 sub-score 0.04 0.26 Amount of videos sub-score 2.458.99 Channel views sub-score 1.11 5.40 Feedback sub-score −0.7125 0

The above table is representative of the various sub-scores used in thecalculation of the final score for a content provider 185. The tableillustrates each sub-scores raw sub-score value and sub-score value. Thesub-score values are then used in the calculation of the final scoreusing the final score algorithm as was previously described:finScore=0.3·subscribe+0.05·totViews+0.1·view100+0.25·view1000+0.05·amtVid+0.15·chaView+0.1·feedback

Using the sub-score values shown in the table above, an example finalscore for a content provider 185 would be equal to a value of 3.38. Inone embodiment, any content provider 185 that receives a final scoreless than a predetermined final score threshold value is automaticallydenied from joining the revenue sharing partner program. For example, afinal score threshold could have a value of 6. Thus, the contentprovider 185 in the example above would be denied from joining therevenue sharing partner program as the content provider 185 did notreceive a final score value indicating that the content provider 185 iseligible to become a revenue sharing partner. Alternatively, even thougha content provider 185 received a final score value less than thepredetermined threshold value, a qualitative judgment may be performedby a system administrator of the video hosting website 100 to determineif the content provider 185 should be invited to become a revenuesharing partner.

In one embodiment, content providers 185 who receive a final scoregreater than the predetermined final score threshold value will beautomatically accepted in the revenue sharing partner program.Alternatively, content providers 185 who receive a score greater thanthe final score threshold will result in review of the contentprovider's uploaded videos to determine video originality. In analternative embodiment, given multiple applicants who received a finalscore greater than the predetermined final score threshold, theapplicant with the highest final score will have his or her uploadedvideos analyzed to determine video originality, as will be furtherdescribed below. Thus, the final score also indicates the priority ofapplicants for review.

Referring back to FIG. 3, in step 305 the application analysis module120 analyzes videos uploaded by content providers 185 who have a finalscore 915 greater than the predetermined final score threshold and atolerable strike status 909 value based on video originality. Originalvideos are considered videos to which the content provider 185 owns thecopyrights and distribution rights for all audio and video content. Inone example, a video uploaded by a content provider 185 illustrating thecontent provider 185 performing a cover song may not be consideredoriginal because the content provider 185 may not own the rights to thesong.

Generally, the application analysis module 120 is in communication withthe video analysis module 120 that compares each of the contentproviders' uploaded videos against videos stored in the video database155 that are considered reference sources to determine if a contentprovider's video is original. The video analysis module 130 determinesif a video is original by using known systems and methods for matchinguploaded digital content items against reference sources, described forexample in U.S. patent application Ser. Nos. 11/765,292 and 11/746,339,each of which is incorporated by reference herein.

In one embodiment, a certain percentage of the content provider's videosmust be original in order for the video to be deemed original. The videoanalysis module 130 determines an originality percentage of the contentprovider's videos. The originality percentage indicates the percentageof the content provider's videos that are considered original. Theoriginality percentage is compared to a predefined threshold percentageto determine whether the originality percentage of the content provider185 is above the predefined threshold percentage. The video analysismodule communicates the results to the application analysis module 120.

Generally, at this point in the revenue sharing partner applicationprocess, all videos being analyzed belong to content providers who havea final score 915 greater than the predetermined final score thresholdvalue and a tolerable strike status 909. Content providers 185 who havean originality percentage greater than the predefined thresholdpercentage will be invited to the revenue sharing partner applicationprocess. Content providers 185 with an originality percentage less thanthe predefined threshold percentage will not be invited to the revenuesharing partner application process. Alternatively, a systemadministrator of the video hosting website 100 may determine whethercontent providers 185 with an originality percentage less than thepredefined threshold percentage should still be invited to the revenuesharing partner application process.

In an alternative embodiment, a system administrator of the videohosting website 100 may review the videos uploaded by the contentprovider 185 to perform a qualitative judgment if the videos areoriginal. The system administrator may review revenue sharing partnerapplications in an order based at least in part on the final scores ofthe received applications. The system administrator utilizes the finalscore values to properly allocate his or her time of reviewingapplications of content providers 185 that would be the most valuable tothe revenue sharing partner program. After the originality of thecontent provider's video is determined, the functional steps in stage203 of the revenue sharing application process are complete.

Referring back to FIG. 2, in stage 205 of the revenue sharing partnerapplication process, the content provider 185 who requested to join therevenue sharing partner program is notified of the decision whether heor she has been invited to become a revenue sharing partner. Thenotification may be in the form of an e-mail or a message in the contentprovider's account in the video hosting website 100. In an alternativeembodiment, content providers 185 that did not request to become revenuesharing partners also receive an invitation. During predefined timeintervals, the application analysis module 120 searches the userdatabase 150 for all content providers 185 in the video hosting website100. The application analysis module 120 performs the steps describedabove to determine content providers 185 that are eligible to become arevenue sharing partner. The eligible content providers 185 that aredetermined eligible to become a revenue sharing partner are also sent aninvitation to become a revenue sharing partner.

To summarize, in one embodiment content providers 185 must meet thefollowing criteria before being invited into the revenue sharing partnerprogram: a tolerable number of strikes, a final score 915 above apredetermined final score threshold and a certain percentage of originalvideos. Content providers 185 that meet the criteria are accepted intothe revenue sharing partner program. In an alternative embodiment, asystem administrator of the video hosting website 100 may determinewhich combination of the criteria discussed above must be met in orderto be invited into the revenue sharing partner program.

Content providers 185 that are invited into the revenue sharing partnerprogram are sent a notification of the invitation as shown in invitationuser interface 1000 in FIG. 10. FIG. 10 is one embodiment of aninvitation user interface 1000 that indicates to the content provider185 that they have been admitted in the revenue sharing partner program.The invitation user interface 1000 also includes important referencematerial for the new revenue sharing partner to review.

In one embodiment, all invited content provider 185 must complete arevenue sharing partner tutorial indicated by the partner tutorial link1001. The revenue sharing partner tutorial helps newly initiated revenuesharing partners understand the revenue sharing partner program's keyconcepts such as how videos generate revenue, how to enable a video forrevenue sharing and/or how to make sure that videos are eligible forrevenue sharing.

In one embodiment, content providers 185 must also sign up for anadvertisement serving program such as Google AdSense. Revenue sharingpartners enroll in the advertisement serving program to allow webadvertisements to be placed on their websites. In an alternativeembodiment, revenue sharing partners are not required to have webadvertisements placed on their websites through the advertisementserving program. Additionally, the advertisement serving programestablishes a mechanism for receiving payments for revenue generated bythe web advertisements placed in a revenue sharing partner's website. Ina further embodiment, revenue sharing partners enroll in theadvertisement serving program only to receive payment. As revenuesharing partners typically provide information such as bank informationfor receipt of payment or a residence or business address where therevenue sharing partner can receive payment, the enrollment in theadvertisement serving program also enables the video hosting website 100to verify the revenue sharing partner's identity since personalinformation such as bank information must be disclosed.

Once a newly invited revenue sharing partner has completed the revenuesharing partner tutorial and enrolled in an advertisement servingprogram, the revenue sharing partner's account is activated for revenuesharing and the revenue sharing partner application process isconcluded. The revenue sharing partner is now able to monetize videos toreceive shared revenue as will be further described below.

Video Monetization Process

The video monetization process is performed by the video analysis module130 to determine if a video uploaded by a revenue sharing partner shouldbe monetized. As previously discussed, a revenue sharing partnerreceives a share of the revenue generated from ad impressions occurringwhen monetized videos associated with the revenue sharing partner areviewed by users of the video hosting website 100.

Referring now to FIG. 4, the video monetization process according to oneembodiment has the following functional stages:

401: Receiving a video monetization request;

403: Determining whether to monetize video; and

405: Updating monetization status.

The first stage 401 entails receiving a request for monetization of avideo. A request for monetization can be received when a revenue sharingpartner uploads videos to the video hosting website 100. Referring toFIG. 11, there is shown an example video upload user interface 1100 inaccordance with one embodiment of the present invention. A revenuesharing partner clicks the browse button 1101 to specify the file pathof the video that the revenue sharing partner wishes to upload to thevideo hosting website 100. To enable monetization of the video, arevenue sharing partner must submit the video for revenue sharing (i.e.,monetization). The revenue sharing partner clicks the revenue sharingcheckbox 1103 to indicate that he or she is requesting that the video beapproved for revenue sharing. Revenue sharing partners are not requiredto submit each video they upload to be enabled for revenue sharing.Revenue sharing partners that do not wish to enable a video formonetization simply specifies the file path of the video using thebrowse button 1101 and uploads the video to the video hosting website100 using the upload video button 1109.

To assist in the approval of the request for revenue sharing of a video,revenue sharing partners provide details of the nature and origin of thecontent included in the video that is being uploaded in the notes field1105. Generally, revenue sharing partners give explanations of thecontent of the video in the notes field 1105 that will be used in theevaluation of the video. Any information that revenue sharing partnerscan provide about the source of the music or visual images used in theuploaded videos will assist in the approval of the video formonetization. Additionally, a statement whether the music or visualimages used in the video have been included with the permission of thesource or the person appearing in the video will assist in the approvalof the video for monetization. For example, a statement in notes field1105 may be “This video consists entirely of footage of me giving areview of the Macbook Pro.”

The video upload user interface 1100 includes a warning 1111 thatindicates if the video being uploaded is not approved for revenuesharing, the video will be removed from the video hosting website 100.Revenue sharing partners run the risk of having their videos removedfrom the video hosting website 100 if the videos submitted formonetization are not approved. Revenue sharing partners are provided ageneral disclaimer 1107 that provides information regarding the type ofcontent that should not be uploaded to the video hosting website. Thegeneral disclaimer 1107 assists in the decision if the video is eligiblefor revenue sharing. If the revenue sharing partner still wishes tosubmit the video for revenue sharing, the revenue sharing partnersubmits the video to the video hosting website 100 using the uploadvideo button 1109.

After clicking the upload video button 1109, the video hosting website100 receives the video and the ingest module 115 processes the video forstorage in the video database 155 as previously discussed. Newlyuploaded videos are made private so that only the revenue sharingpartner who uploaded the video can view the video. In an alternativeembodiment, newly uploaded video are made public to the users of thevideo hosting website 100, but the videos are not shown in conjunctionwith web advertisements.

Alternatively, videos that were not initially submitted for revenuesharing or videos that the revenue sharing partner uploaded prior tobeing accepted in the revenue sharing partner program can be enabled forrevenue sharing. Referring now to FIG. 12, there is shown an example ofa revenue sharing partner's video user interface 1200 in one embodimentof the present invention. The video user interface 1200 illustrates tothe revenue sharing partner videos which have not been enabled formonetization. The video user interface 1200 is comprised of one or morevideo rows 1201. A single video row is associated with a single videoand comprises a video avatar 1211. The video avatar 1211 may be a stillframe excerpt of the video or a moving frame excerpt. The video avatar1211 assists the revenue sharing partner in the decision whether thevideo should be enabled for revenue sharing as the revenue sharingpartner can see a portion of the content in the video. Additionally,revenue sharing partners can use the video user interface 1200 to uploadvideos to the video hosting website using the upload button 1209.

A video information section 1213 is also included in the video row 1201.The video information section 1213 illustrates general informationassociated with the video including video title, video length, URL linkto the video on the video hosting website 100, date that the video wasadded to the video hosting website 100 and the raw file name. Revenuesharing partners are able to edit the video information section 1213using the edit video info button 1205.

More importantly, the video information section 1213 includes feedbackinformation from users of the video hosting website 100. The feedbackinformation includes the average star rating, the number of views thevideo received and the number of comments the video received. Thisfeedback information indicates to the revenue sharing partner if thevideo is a good candidate for monetization as a video with a largenumber of views can potentially generate more revenue compared to avideo with a lower number of views, for example.

After reviewing the videos in the video user interface 1200, a revenuesharing partner can indicate that he or she wants to submit a video formonetization. Each video row 1201 includes a video checkbox 1203. Thevideo checkbox 1203 is used to indicate which video will be enabled forrevenue sharing. Additionally, each video row 1201 includes an enablerevenue sharing button 1207. The enable revenue sharing button ispressed if a revenue sharing partner wants to request a particular videobe monetized. For example, a revenue sharing partner can click on thecheckbox that is associated with the video that will be enabled forrevenue sharing and press the enable revenue sharing button that isassociated with the checkbox. After clicking on the enable revenuesharing button 1207, the revenue sharing partner is directed to a videoconfirmation user interface 1300 as shown in FIG. 13.

The video confirmation user interface 1300 allows revenue sharingpartners to provide details of the nature and origin of the contentincluded in the video that is being uploaded in the notes field 1301.These details will assist in the approval of the request, as waspreviously discussed with regard to videos that were enabled formonetization during their initial upload. Revenue sharing partners aredisplayed a warning 1303. The warning 1303 indicates to revenue sharingpartners that they risk having their videos, which are alreadypublically displayed, removed from the video hosting website 100 if thevideos are not approved. Revenue sharing partners who do not want torisk having their videos removed may click the cancel button 1307.Revenue sharing partners that still wish to have their video enabled formonetization can click on the submit button 1305.

Once the revenue sharing partner has submitted a request formonetization of a video to the video hosting website 100, the video mustbe reviewed prior to being enabled for monetization. The second stage403 of the video monetization process determines whether to monetize avideo that has been requested for monetization. FIG. 5 is representativeof the steps performed by the video analysis module 130 in the secondstage 403. The second stage 403 comprises the following functional stepsto determine whether a video should be monetized to allow a revenuesharing partner to receive revenue generated by web advertisements shownwith the monetized video:

501: Comparing video against reference sources;

503: Determining length of partnership of the revenue sharing partner;and

505: Analyzing video according to the length of partnership.

In the first step 501, the submitted video is compared against referencesources. The video analysis module 130 compares videos that have beensubmitted for monetization against reference sources to ensure that thevideos are original. Original videos are considered videos which thecontent provider 185 owns the copyrights and distribution rights for allaudio and video content that is uploaded. For example, a videoillustrating a person drawing a picture of a Ferrari on an Etch-A-Sketchtoy may be considered an original video. In another example, a videouploaded by a content provider 185 illustrating the content provider 185performing a cover song may not be considered original because thecontent provider 185 may not own the rights to the song. As previouslydescribed above, the video analysis module 130 utilizes systems andmethods for matching uploaded digital content items against referencecontent are known, and some are described for example in U.S. patentapplication Ser. Nos. 11/765,292 and 11/746,339, each of which isincorporated by reference herein.

In one embodiment, videos that are matched to a reference source by thevideo analysis module 130 are automatically denied being monetized. Therevenue sharing partner that submitted the request for monetization ofthe denied video is notified that the video has been denied and that thevideo will be removed from the video hosting website 100. In analternative embodiment, videos that are matched to a correspondingreference source are manually reviewed by a system administrator of thevideo hosting website 100. The system administrator will make thedecision whether the video contains original content.

In step 503, the length of partnership of the revenue sharing partner isdetermined. If a video did not match any reference source, the amount oftime the revenue sharing partner has been part of the revenue sharingpartner program is determined. In one embodiment, the length ofpartnership dictates if an analysis is performed on the video submittedfor monetization. The video analysis module 130 determines the length ofpartnership of the revenue sharing partner requesting monetization of avideo by extracting the information from the revenue sharing partner'saccount record stored in the user database 150. Once the partnershiplength is determined, the video analysis module can begin to analyze thevideo.

In step 505, videos submitted for monetization that did not match anyreference source are analyzed. The video analysis module 130 reviewsvideo information related to the video submitted for monetization alongwith the strike status of the revenue sharing partner. As previouslydiscussed, a revenue sharing partner may receive strikes to his or heraccount if a take down request of one of the revenue sharing partner'svideos is processed. The video analysis module 130 reviews theinfraction information stored in the account record of the revenuesharing partner in the user database 150. Revenue sharing partners mustmaintain proper behavior and follow the rules of conduct of the videohosting website 100 if they wish to have their videos monetized. In oneembodiment, the number of strikes against the revenue sharing partnersince they joined the revenue sharing partner program is analyzed. Inone embodiment, if the revenue sharing partner has received a strikeagainst his or her account, videos submitted for monetization areautomatically rejected and removed from the video hosting website 100.In an alternative embodiment, if the revenue sharing partner has anumber of strikes greater than a predefined strike threshold, the videois automatically rejected for monetization and removed from the videohosting website. The predefined strike threshold can be set by a systemadministrator of the video hosting website 100 to determine the numberof strikes a revenue sharing partner may receive that will preventmonetization of a video. In an alternative embodiment, a systemadministrator can manually review the strike status of the revenuesharing partner to aid in the determination if the video submitted bythe revenue sharing partner should be monetized. If the revenue sharingpartner did not receive any strikes against his or her account, videoinformation related to the video is reviewed as further described below.

In one embodiment, video information includes feedback information suchas the number of views a video received, the number of rating stars avideo has received or the number of users that have rated the video.Generally, the feedback information is compared to a feedback thresholdassociated with the particular type of feedback information. The numberof views a video received indicates to the video analysis module 130 thepopularity of the video. The video analysis module 130 retrieves thenumber of views a video has received from the video record in the videodatabase 155 and compares the number of views to a predefined popularitythreshold. Videos which receive an amount of views greater than thepopularity threshold are considered popular. In one embodiment, popularvideos are automatically monetized as long as the revenue sharingpartner did not have a strike status above the strike threshold. Popularvideos are automatically monetized since popular videos can potentiallygenerate a large amount of revenue since many users view these videos.

The number of rating stars a video has received and the number of usersthat have rated the video indicates the quality of the video and can beused to determine an average rating of the video. Videos that have anaverage star rating greater than a predefined average star ratingthreshold may be allowed to be monetized. For example, videos with anaverage star rating of 4 out of 5 stars are allowed to be monetized.Videos with an average star rating greater than the star ratingthreshold are said to be quality videos. Quality videos are generallyenjoyed by users of the video hosting website 100 and are monetized asthere is generally a correlation between the quality of a video and thenumber of views a video receives. For example, videos with a highquality rating generally have a high number of views or may eventuallyreceive a high number of views through word of mouth of the users of thevideo hosting website 100. Users may inform other users of the qualityvideos by posting the video on websites 175 other than the video hostingwebsite or by sending the URL link of the quality video to other users.

Videos undergo the analysis described above depending on the length ofpartnership of the revenue sharing partner who submitted the video thatwas determined in step 503. The amount of time a revenue sharing partnerhas been part of the revenue sharing partner program dictates whetherhis or her videos undergo the analysis described above. In oneembodiment, the length of time that the revenue sharing partner has beenpart of the revenue sharing partner program dictates whether a videofrom a revenue sharing partner will be reviewed. The length of time iscompared against various defined time intervals to determine whether avideo should be analyzed.

In one embodiment, within a first length of time that a revenue sharingpartner joined the revenue sharing partner program, every videosubmitted by the revenue sharing partner is analyzed as described above.For example, within the first two months that a revenue sharing partnerjoined the revenue sharing partner program, every video submitted by therevenue sharing partner is analyzed. New revenue sharing partners havenot established any credibility as a revenue sharing partner. Thus,every video of new revenue sharing partners must be analyzed. Revenuesharing partners must follows the rules of the video hosting website 100and only upload original content in order to gain credibility on thevideo hosting website 100.

In one embodiment, after a second length of time of becoming a revenuesharing partner, all videos uploaded by the revenue sharing partner areautomatically monetized. At this point, the revenue sharing partner hasgained enough credibility that his or her videos no longer need to beanalyzed for monetization. For example, every video submitted after thethird month since the revenue sharing partner joined the revenue sharingpartner program is automatically approved. In order to ensure revenuesharing partners are still abiding by the rules of the video hostingwebsite 100, the analysis discussed above may be performed on a yearlybasis, for example, to ensure that the revenue sharing partner is notabusing his or her credibility. The time intervals mentioned above aremerely exemplary of time intervals that can be used in the determinationto monetize a video. Any suitable time interval can be used asdetermined by the system administrator of the video hosting website 100.

In one embodiment, videos submitted between the first length of time andthe second length of time that a revenue sharing partner joined therevenue sharing partner program are not always analyzed. Only a certainpercentage of videos submitted for monetization are analyzed. Forexample, during the third month of becoming a revenue sharing partner,only 75% of videos submitted by the revenue sharing partner are reviewedfor monetization. At this point, the revenue sharing partner has gainedcredibility since the revenue sharing partner has shown during the firsttwo months of partnership that he or she can abide by the rules of thevideo hosting website and only upload original videos.

In one embodiment, a prevention mechanism is implemented to preventvideos from automatically being monetized from revenue sharing partnerswho did not request any videos for monetization up to the second lengthof time. The video analysis module 130 reviews the number of requests ofmonetization since the time when the revenue sharing partner joined therevenue sharing partner program up until the second length of time. Ifthe revenue sharing partner did not submit any requests for monetizationup until the second length of time, the revenue sharing partner's videosare analyzed by the video analysis module 130 regardless if they aresubmitted after the second length of time.

Referring back to FIG. 4, during the third stage 405 of the videomonetization process, the video analysis module 130 updates themonetization status of videos submitted for monetization. The accountrecords in the video database 155 of videos that have been enabled formonetization are updated to indicate that the videos are capable ofgenerating revenue through placement of web advertisements shown onpages including the monetized video. Videos which have been denied aredeleted from the video database 155.

In one embodiment, videos which have been monetized are removed from thevideo user interface 1200 and are placed in the revenue sharing videosuser interface 1400 as shown in FIG. 14. The revenue sharing videos userinterface 1400 illustrates all the monetized videos associated with therevenue sharing partner. Revenue sharing partners may view all theirmonetized videos and can decide to disable the video for revenuesharing. The revenue sharing videos user interface 1400 is similar tothe video user interface 1200. The revenue sharing videos user interface1400 comprises video rows 1401 that is associated with a single videoand comprises the same features described in the video user interface1200. In addition, the revenue sharing videos user interface 1400comprises a disable revenue sharing button 1403. Revenue sharingpartners may disable videos from receiving revenue if they decide toremove the video from the video hosting website 100 or for any otherappropriate reason.

Revenue Generation

Videos which have been enabled for monetization are displayed inconjunction with a web advertisement. Referring to FIG. 15, there isshown an example video display user interface 1500 according to oneembodiment. The video display user interface 1500 comprises a monetizedvideo shown in the display region 1501. Additionally, a webadvertisement 1503 is shown in conjunction with the monetized video.Revenue sharing partners generate revenue (i.e., money) from the webadvertisements 1503 shown in conjunction with their monetized video. Themethod that revenue is generated depends on the type of webadvertisement displayed with the monetized video. The amount of revenuegenerated by revenue sharing partners is tracked by the revenuegeneration module 135. The different types of advertisements and howthese types of advertisements generate revenue will now be described.

As shown in the revenue sharing videos user interface 1400, in oneembodiment the web advertisement 1503 is placed to the right of themonetized video. Web advertisements that are placed outside of themonetized video, such as web advertisement 1503 in FIG. 15, areconsidered external web advertisements as they are displayed separatelyfrom the monetized video. Additionally, pop-ups or web advertisementsthat automatically appear in a new web page may appear after themonetized video has finished playing. Pop-ups are also consideredexternal web advertisements. Pop-ups may also appear automatically aftera monetized video begins playing or after a certain duration of thevideo has passed. Additionally, pop-ups may appear as a result of a userclicking on web-advertisements that are placed outside of the monetizedvideo. Users would be displayed additional web advertisements pertainingto the web advertisement that was clicked. For example, webadvertisement 1503 displays an advertisement of a new automobile. If auser clicks on the web advertisement 1503, a new web page would bedisplayed containing another web advertisement of the same automobile orother automobiles of the same make.

Web advertisements need not be shown in a separate area from themonetized video as shown in the video display user interface 1500. Webadvertisements displayed in the display region 1501 with the monetizedvideo are considered internal web advertisements. In one embodiment,when a user starts to view a video by pressing the play button 1505, anadvertisement will be played somewhere in the video display region 1501that does not obstruct the viewing of the content of the video. The webadvertisement is essentially overlaid onto the video content. Forexample, the advertisement may be placed on the bottom right corner ofthe monetized video or somewhere along the bottom edge of the monetizedvideo so not to obstruct the video content. Alternatively, a webadvertisement may be played in the display region 1501 prior to theplayback of the monetized video. For example, if a user clicks on theplay button 1505, a web advertisement would be displayed prior to themonetized video being displayed. A web advertisement also may be playedin the display region 1501 after the duration of the monetized video haselapsed.

Revenue sharing partners may generate revenue in various ways. In oneembodiment, revenue may be generated based on payment per view. Forexternal web advertisements which merely are displayed separately fromthe monetized video, a revenue sharing partner may generate revenue eachtime the web advertisement is shown in conjunction with the monetizedvideo. External web advertisements such as pop-ups that appearautomatically after a monetized video begins playing or after a certainduration of the video has passed also can generate revenue each time thepop-up appears. For internal web advertisements, a revenue sharingpartner may generate revenue as long as a portion of the monetized videois played. In an alternative embodiment, a revenue sharing partner mayonly generate revenue if the duration of the entire web advertisement isplayed.

The revenue generation module 135 tracks the number of views themonetized video received from users of the video hosting website 100.The number of views is tracked as the number of views a video receivedcorrelates to the number of times a web advertisement was viewed. Usingthe number of views value the monetized video received, the revenuegeneration module 135 can calculate the revenue generated based on arate per view value. The rate per view value may be set by the systemadministrator of the video hosting website 100 or may be automaticallyset by the application analysis module 120 when the revenue sharingpartner was invited into the revenue sharing program. For example, arevenue sharing partner may have a rate per view value of $0.001 forevery view. The revenue generation module 135 may determine that arevenue sharing partner has received a total of 1,000 views for all hisor her monetized videos. Thus, the revenue sharing partner will havegenerated $1.00 from his or her monetized videos in one example.

In one embodiment, the rate per view is the same for every revenuesharing partner. A set rate per view value may be determined by thesystem administrator depending on the length of partnership of a revenuesharing partner. In an alternative embodiment, the rate per view isbased on the length of partnership. Revenue sharing partners who havebeen part of the revenue sharing partner program for a determined lengthof time will have a higher rate per view compared to newly joinedrevenue sharing partners. Thus, the rate per view value of each revenuesharing partner will increase as their length of partnership increases.

In another embodiment, revenue may be generated based on payment perclick. External web advertisements such as pop-ups generate revenue eachtime a user of the video hosting website 100 clicks on an external webadvertisement such as web advertisement 1503. Clicking of webadvertisement 1503 would cause a web page containing another webadvertisement to be played. The revenue generation module 135 tracks thenumber of times users of the video hosting website 100 clicks on webadvertisements shown in monetized videos associated with each of therevenue sharing partners. For revenue generated by payment per click,each revenue sharing partner is assigned a rate per click value. Therate per click value is similar to the rate per view value. The rate perclick value may be set by the system administrator of the video hostingwebsite 100 or may be automatically set by the application analysismodule 120 when the revenue sharing partner was invited into the revenuesharing program. Like the rate per view, the rate per click may be thesame for every revenue sharing partner or may be different depending onthe length of partnership of the revenue sharing partner.

In an alternative embodiment, revenue sharing partners may receive ashare percentage of revenue generated by web advertisements placed inconjunction with their monetized videos. Companies may negotiate a flatpayment to the owners of the video hosting website 100 for displayingtheir web advertisements. Revenue sharing partners that display webadvertisements of that company would receive a percentage of the revenuethat the owners of the video hosting website 100 received. For example,assume that a company paid the owners of the video hosting website$10,000 to host their advertisements and 1,000 revenue sharing partnersdisplay those web advertisements. Thus, each revenue sharing partnergenerated $10 of revenue for displaying the company's webadvertisements. The revenue sharing partners would only receive a setpercentage of the generated revenue. For example, the set percentage maybe 50% of the revenue generated, thus each revenue sharing partner wouldreceive $5.00.

Alternatively, companies may negotiate a rate per view or rate per clickscheme as described above and revenue sharing partners may receive apercentage of the revenue generated that is shared with the owners ofthe video hosting website 100. For example, assume that the companynegotiated with the owners of the video hosting website a rate of $1 perview of the company's commercials. If a revenue sharing partner received100 views of the company's commercials, the revenue sharing partnergenerated $100. The generated revenue is then shared with the owners ofthe video hosting website 100 based on a share percentage. The sharepercentage may be a fixed value for all revenue sharing partners or maybe different depending on the length of partnership as previouslydescribed.

The features described herein beneficially provide a system and methodto admit content providers of a video hosting website into a revenuesharing partner program where the content providers may submit videosfor monetization in order to generate shared revenue. Revenue sharingallows content providers to receive compensation for their originalvideos.

Some portions of above description describe the embodiments in terms ofalgorithms and symbolic representations of operations on information.These algorithmic descriptions and representations are commonly used bythose skilled in the data processing arts to convey the substance oftheir work effectively to others skilled in the art. These operations,while described functionally, computationally, or logically, areunderstood to be implemented by computer programs or equivalentelectrical circuits, microcode, or the like. Furthermore, it has alsoproven convenient at times, to refer to these arrangements of operationsas modules, without loss of generality. The described operations andtheir associated modules may be embodied in software, firmware,hardware, or any combinations thereof.

As used herein any reference to “one embodiment” or “an embodiment”means that a particular element, feature, structure, or characteristicdescribed in connection with the embodiment is included in at least oneembodiment. The appearances of the phrase “in one embodiment” in variousplaces in the specification are not necessarily all referring to thesame embodiment.

As used herein, the terms “comprises,” “comprising,” “includes,”“including,” “has,” “having” or any other variation thereof, areintended to cover a non-exclusive inclusion. For example, a process,method, article, or apparatus that comprises a list of elements is notnecessarily limited to only those elements but may include otherelements not expressly listed or inherent to such process, method,article, or apparatus. Further, unless expressly stated to the contrary,“or” refers to an inclusive or and not to an exclusive or. For example,a condition A or B is satisfied by any one of the following: A is true(or present) and B is false (or not present), A is false (or notpresent) and B is true (or present), and both A and B are true (orpresent).

In addition, use of the “a” or “an” are employed to describe elementsand components of the embodiments herein. This is done merely forconvenience and to give a general sense of the invention. Thisdescription should be read to include one or at least one and thesingular also includes the plural unless it is obvious that it is meantotherwise.

Upon reading this disclosure, those of skill in the art will appreciatestill additional alternative structural and functional designs for asystem and a process for collaboratively ranking a set of digitalcontent items through the disclosed principles herein. Thus, whileparticular embodiments and applications have been illustrated anddescribed, it is to be understood that the disclosed embodiments are notlimited to the precise construction and components disclosed herein.Various modifications, changes and variations, which will be apparent tothose skilled in the art, may be made in the arrangement, operation anddetails of the method and apparatus disclosed herein without departingfrom the spirit and scope defined in the appended claims.

What is claimed is:
 1. A computer-implemented method to categorize videocontent providers, comprising: receiving, by one or more computingdevices, a request from a provider of video content to receive contentitems to present in conjunction with video content presented by thevideo content provider; analyzing, by the one or more computing devices,a set of video content presented by the video content provider;determining, by the one or more computing devices, that the set of videocontent has a minimum number of viewers and meets a standard for uploadcontent; and in response to determining that the set of video contenthas the minimum number of viewers and meets the standard for uploadcontent and originality and based on a video upload frequency of theprovider of the video content, communicating, by the one or morecomputing devices, a content item to the video content provider topresent in conjunction with video content.
 2. The computer implementedmethod of claim 1, wherein the video content items are determined to beoriginal based on a digital fingerprinting of the video content items.3. The computer implemented method of claim 1, further comprisingtransferring, by the one or more computing devices and to the videocontent provider, a portion of received revenue from the content item.4. The computer implemented method of claim 1, wherein the content itemis presented by the video content provider at a time before the videocontent provider presents the video content.
 5. The computer implementedmethod of claim 4, wherein the request is received as an onlineapplication.
 6. The computer implemented method of claim 5, wherein therevenue is generated when a certain number of viewers are presented thecontent item.
 7. The computer implemented method of claim 4, wherein therevenue is generated when a viewer clicks on the content item.
 8. Thecomputer implemented method of claim 1, wherein the revenue is generatedwhen a viewer takes an action based on the content item.
 9. The computerimplemented method of claim 1, wherein the standard for upload contentis based on a number of violations of a set of conduct rules establishedby the one or more computing devices.
 10. The computer implementedmethod of claim 1, wherein the standard for upload content is based on anumber of video content items submitted by the provider.
 11. Thecomputer implemented method of claim 1, wherein the standard for uploadcontent is based on a number of video content items that are determinedto be original.
 12. The computer implemented method of claim 1, furthercomprising: determining, by the one or more computing devices, that theset of video content has been viewed for a minimum cumulative amount oftime; and in response to determining that the set of video content hasbeen viewed for the minimum cumulative amount of time, communicating, bythe one or more computing devices, a content item to the video contentprovider to present in conjunction with video content.
 13. A computerprogram product, comprising: a non-transitory computer-readable storagedevice having computer-executable program instructions embodied thereonthat when executed by a computer cause the computer to categorize videocontent providers, the computer-executable program instructionscomprising: computer-executable program instructions to receive arequest from a provider of video content to receive content items topresent in conjunction with video content presented by the video contentprovider; computer-executable program instructions to analyze a set ofvideo content presented by the video content provider;computer-executable program instructions to determine that the set ofvideo content has a minimum number of viewers and meets a standard forupload content; and computer-executable program instructions tocommunicate a content item to the video content provider to present inconjunction with video content in response to determining that the setof video content has the minimum number of viewers and meets thestandard for upload content and originality and based on a video uploadfrequency of the provider of the video content.
 14. The computer programproduct of claim 13, wherein the video content items are determined tobe original based on a digital fingerprinting of the video contentitems.
 15. The computer program product of claim 13, further comprisingtransferring, by the one or more computing devices and to the videocontent provider, a portion of received revenue from the content item.16. The computer program product of claim 13, wherein the content itemis presented by the video content provider at a time before the videocontent provider presents the video content.
 17. A system to categorizevideo content providers, comprising: a storage device; a network device;and a processor communicatively coupled to the storage device and thenetwork device, wherein the processor executes application codeinstructions that are stored in the storage device to cause the systemto: receive a request from a provider of video content to receivecontent items to present in conjunction with video content presented bythe video content provider; analyze a set of video content presented bythe video content provider; determine that the set of video content hasa minimum number of viewers and meets a standard for upload content; andcommunicate a content item to the video content provider to present inconjunction with video content in response to determining that the setof video content has the minimum number of viewers and meets thestandard for upload content and originality and based on a video uploadfrequency of the provider of the video content.
 18. The system of claim17, wherein the content item is presented by the video content providerat a time before the video content provider presents the video content.19. The system of claim 17, wherein the request is received as an onlineapplication.
 20. The system of claim 17, wherein the revenue isgenerated when a viewer clicks on the content item.